home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
utility
/
ccache11.zip
/
OVERVIEW.TXT
< prev
next >
Wrap
Text File
|
1996-06-22
|
19KB
|
532 lines
OVERVIEW COPYRIGHT 1995-1996 horio shoichi OVERVIEW
NAME
overview.txt - Overview Of Concache.exe
About Concache.exe
Concache.exe is for "concurrent disk cache" that is so
called "advance cache", which drives disks concurrently with
DOS/user programs. The maximum concurrency it can perform is
up to 25 disks, including one of two floppies, one of IDE
disks, and up to maximum number of configurable SCSI disk
units under DOS. (The term IDE is for Integrated Device
Interface. In this and the other texts in this package, how-
ever, includes ST506 interface and ESDI for brevity.)
Concache.exe allows true preread/postwrite operations trans-
parently for programs under DOS.
The basic idea to attain concurrency is, by catching PC/AT
type machine's BIOS int1590 and int1591 interrupts, to force
switch from concache.exe to DOS/user program by the former
and force back again to concache.exe by the latter.
The SCSI hard disks are operated concurrently by the aid of
ASPI (Advanced SCSI Programming Interface) command posting
capability, which offers the chance to synchronize with disk
operations exactly the same way as BIOS int1590/int1591
allows.
Additional programs floppies.exe and ccdisk.exe are provided
with concache.exe, the main cache program. The former is a
mini-driver which does most of floppy i/o independent of
DOS. The latter is the reentrant disk driver for SCSI disks,
using ASPI.
If a disk is neither of above, for example pre-ASPI SCSI
disk, concurrency is lost there. On such disk, the interval
the device made CPU idle is indiscernible from CPU overhead.
Yet postwrite, although not concurrently, is supported for
such disks.
Prerequisites
Concache.exe runs PC/AT class machine and after, equipped
with INTEL 80386 CPU and the later, running MSDOS3.1 and the
later or the equivalents.
Concache.exe resident memory requirements are usually around
25 - 30 kilobytes, increased depending on concurrency
requirements (stacks to keep things concurrent and sheer io
buffers are unavoidably allocated at each startup.)
Concache 1.10 Last Update: 22 June 1996 1
OVERVIEW COPYRIGHT 1995-1996 horio shoichi OVERVIEW
Cache Data Area
Concache.exe uses memory for caching disk data. Memory types
to be used are
1) Raw protected (int15) memory,
2) Expanded memory conformable to EMS specification 4.0,
3) Extended memory block (EMB) defined by XMS 2.0 specifi-
cation.
If only int15 memory is to be used no additional third party
software is needed.
If memory manager allows configure, these three types of
memory can be used freely mixed, totaling up to 64
megabytes. The amount of EMS or EMB used by concache.exe
are changeable without disloading/reloading concache.exe
from memory. (Int15 memory is hard to share with the other
programs. Changing its size on the fly is not considered.)
Installation
If ROM BASIC is used then interrupt number and the identifi-
cation of the interrupt have to be adjusted using VECTOR
description. Please refer to concache.txt for the explana-
tions. The adjustment must be applied to all the programs
among concache.exe, ccdisk.exe, and floppies.exe you intend
to use.
Otherwise there is no need of installation procedure. Dis-
able disk cache program currently used, and simply copy to
convenient place and make calls, either from DOS config.sys,
autoexec.bat, or command line, as appropriate.
Quick Test
Real programmers may skip to the next section. (Virtuals may
better not.)
If your system is fairly recent one and you believe it is
configured in just standard way, and you have read the Known
Incompatibilities section below, and is not running the
other disk cache program, and currently on command line from
command.com, then you can test if your system runs con-
cache.exe.
Afterwards, you should read the related documents to find
out what you have done in this test.
Concache 1.10 Last Update: 22 June 1996 2
OVERVIEW COPYRIGHT 1995-1996 horio shoichi OVERVIEW
- First, go to the directory where concache.exe is copied
and type simply "concache". You will see the message
it is not loaded. This message should appear.
- Next, type "concache x". Now concache.exe has allo-
cated memory for its cache area if it doesn't complain.
If it complains, try "concache e" and "concache p" in
this order until you succeed.
If all fails, there is no memory to be used for cache
area, and your quick test has failed. You have to add
memory or you must decrease some other program's memory
usage.
- You should have allocated all available memory of a
type, which could be against your intention. See this
by typing "concache hm", which means "help about memory
usage".
- If you succeeded in "concache p", you can release the
memory by typing "concache d" which means "delete resi-
dent concache.exe from memory". If you have done so,
you might try different amount by typing "concache
p1m", "concache p256k", "concache p131072", and so on,
anything between zero and maximum value reported.
- If you have succeeded in "concache x" or "concache e",
you can try above experiment similarly. Try it later,
substituting "x" or "e" with "p" as appropriate.
For now type "concache xm" or "concache em", which
reallocates zero megabyte (that is, zero byte) memory.
In other words, it has released all allocated memory
but concache.exe is still in memory.
Again type "concache hm" and see it is using none.
You are now be able to allocate as much memory as you
like exactly like the case "concache 'p" but without
doing "concache d". This is an advantage over "concache
p".
- If you have allocated more than 256kb of memory, you
will make an interesting test at this point.
Prepare a spare floppy (it must be formatted, though)
into floppy drive a:, and type "copy concache.exe a:"
(or whatever file), and type "concache hd" immediately.
You have told "help about drives" by typing "concache
Concache 1.10 Last Update: 22 June 1996 3
OVERVIEW COPYRIGHT 1995-1996 horio shoichi OVERVIEW
hd".
You see floppy is being written, and you get the list
of how devices are treated by concache.exe.
You will observe a line "still XX wet spots" which
tells how many blocks of sectors remain to be written
into the floppy a:. If you type "concache hd" again,
then this line is probably unseen.
By allocating larger memory and copying more files at
once into floppy, and typing "concache hd" in succes-
sion, you will observe the number of wet spots decreas-
ing toward zero. Chance to observe this line when hard
disk is used instead of floppy is small unless a large
copy is done using large cache data memory.
If you have succeeded up to this point, your remaining thing
to do is to edit your autoexec.bat or config.sys file. How-
ever, please read on.
You have seen an advantage and a disadvanta